-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkg/machine/e2e: Remove unnecessary copy of machine image. #23068
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ashley-cui The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Initial local run of one test file, but lets see the performance in the full CI run. Before change: After change: |
Me wonders why This PR touches machine so running machine test is correct but why would it trigger bud here?! |
Comparing to https://cirrus-ci.com/build/5300635074035712 it doesn't look like it made a difference for linux. |
Base is very very old, does not include your changes |
Well then I have a bug report for you :) Your logformatter base commit is showing the wrong commit then, i.e. https://api.cirrus-ci.com/v1/artifact/task/5807831486562304/html/sys-remote-rawhide-root-host-sqlite.log.html lists 9ffac33 as base. Unless I am misunderstanding what "base" means. For me it would be last commit on the branch (PR) that is already in main. |
Stop copying the pre-pulled uncompressed machine disk into the individual test dir. The machine pull code already makes a copy of the disk into the test's HOMEDIR/.local/share/containers/podman/machine, and works off that copy. Before the change: TESTDIR/<image> is copied to TESTDIR/podman_test/<image> by the test, and then podman machine copies the image to TESTDIR/podman_test/.local/share/containers/podman/machine/provider/<image> After the change: TESTDIR/<image> is copied to TESTDIR/podman_test/.local/share/containers/podman/machine/provider/<image> by podman machine The image that is actually run is at TESTDIR/podman_test/.local/share/containers/podman/machine/provider/<image> in both instances. Signed-off-by: Ashley Cui <[email protected]>
Rebased against main, and going to look at the test run from that. If the speed gains are lasting then I'll mark as ready for review :) |
And now the skips are working, as this only touches machine test code no sys/int/bud tests triggered. |
Mac test is extremely flakey, but I can't think of a reason why this change would do that, going to dig a little . |
Machine flake is #22551 |
HyperV: 10 min speedup Looks like it sped up the Mac tests a lot, which makes sense, since those machines were still slightly io bound. |
At the least for the other PRs I checked I do not see that much speed up on linux/wsl. There is a lot of variance in the run two run timings so it is hard to tell of course. Of course this is a good to start but we have to get macos/hyperv to around 20 min to achieve our 30 min overall CI time goal. Anyhow LGTM of course |
/lgtm |
Stop copying the pre-pulled uncompressed machine disk into the individual test dir. The machine pull code already makes a copy of the disk into the test's HOMEDIR/.local/share/containers/podman/machine, and works off that copy.
Before the change:
TESTDIR/<image>
is copied toTESTDIR/podman_test/<image>
by the test, and then podman machine copies the image toTESTDIR/podman_test/.local/share/containers/podman/machine/provider/<image>
After the change:
TESTDIR/<image>
is copied toTESTDIR/podman_test/.local/share/containers/podman/machine/provider/<image>
by podman machineThe image that is actually run is at
TESTDIR/podman_test/.local/share/containers/podman/machine/provider/<image>
in both instances.Does this PR introduce a user-facing change?